Skip to content

remote ray client example #833

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

laurafitzgerald
Copy link
Contributor

@laurafitzgerald laurafitzgerald commented May 29, 2025

Issue link

Jira Link

What changes have been made

Add a new additional demo example illustrating submission of Ray jobs to an existing Ray Cluster.

Verification steps

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • Testing is not required for this change

@openshift-ci openshift-ci bot requested review from Bobbins228 and Fiona-Waters May 29, 2025 14:17
Copy link

codecov bot commented May 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.55%. Comparing base (07bdade) to head (94fa053).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #833   +/-   ##
=======================================
  Coverage   92.55%   92.55%           
=======================================
  Files          24       24           
  Lines        1410     1410           
=======================================
  Hits         1305     1305           
  Misses        105      105           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@kryanbeane kryanbeane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

other than comment about token formatting, lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 29, 2025
Copy link
Contributor

@Bobbins228 Bobbins228 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you change the language to Python instead of plain text?

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 29, 2025
@laurafitzgerald laurafitzgerald force-pushed the remote-client-example branch 2 times, most recently from a89a19e to 7a38136 Compare May 29, 2025 14:31
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 29, 2025
@chipspeak chipspeak force-pushed the remote-client-example branch from 7a38136 to 66333e8 Compare June 10, 2025 11:39
@openshift-ci openshift-ci bot removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 10, 2025
@chipspeak chipspeak force-pushed the remote-client-example branch 3 times, most recently from ed39723 to 77e810a Compare June 10, 2025 11:49
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 10, 2025
@chipspeak chipspeak force-pushed the remote-client-example branch 3 times, most recently from 4041e1b to 5e77ce2 Compare June 11, 2025 08:27
@chipspeak chipspeak force-pushed the remote-client-example branch from 5e77ce2 to 4789e33 Compare June 11, 2025 10:02
@laurafitzgerald
Copy link
Contributor Author

/approve
/lgtm

Copy link
Contributor

openshift-ci bot commented Jun 11, 2025

@laurafitzgerald: you cannot LGTM your own PR.

In response to this:

/approve
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Co-authored-by: bkeane <[email protected]>
Co-authored-by: chipspeak <[email protected]>
Co-authored-by: Bobbins <[email protected]>
@chipspeak chipspeak force-pushed the remote-client-example branch from 4789e33 to 94fa053 Compare June 11, 2025 10:07
@chipspeak chipspeak self-requested a review June 11, 2025 10:07
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 11, 2025
Copy link
Contributor

openshift-ci bot commented Jun 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chipspeak, kryanbeane, laurafitzgerald

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [chipspeak,kryanbeane,laurafitzgerald]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@chipspeak chipspeak merged commit 1dc3343 into project-codeflare:main Jun 11, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants